provider Events PUT /api/0/organizations/{organization_id_or_slug}/issues/
@utdk/sentry /api/0/organizations/{organization_id_or_slug}/issues/
Bulk Mutate an Organization's Issues
Bulk mutate various attributes on a maxmimum of 1000 issues. - For non-status updates, the `id` query parameter is required. - For status updates, the `id` query parameter may be omitted to update issues that match the filtering. If any IDs are out of scope, the data won't be mutated but the endpoint will still produce a successful response. For example, if no issues were found matching the criteria, a HTTP 204 is returned.
organization_id_or_slug path required
The ID or slug of the organization the resource belongs to.
string
environment query
The name of environments to filter by.
array
project query
The IDs of projects to filter by. `-1` means all available projects. For example, the following are valid parameters: - `/?project=1234&project=56789` - `/?project=-1`
array
id query
The list of issue IDs to mutate. It is optional for status updates, in which an implicit `update all` is assumed.
array
query query
An optional search query for filtering issues. A default query will apply if no view/query is set. For all results use this parameter with an empty string.
string
viewId query
The ID of the view to use. If no query is present, the view's query and filters will be applied.
string
sort query
The sort order of the view. Options include 'Last Seen' (`date`), 'First Seen' (`new`), 'Trends' (`trends`), 'Events' (`freq`), 'Users' (`user`), 'Date Added' (`inbox`), and 'Recommended' (`recommended`).
enum: date, freq, inbox, new…
limit query
The maximum number of issues to affect. The maximum is 100.
integer

Try it

Authentication
Configure credentials for API Reference
Gateway
The gateway proxies requests and injects credentials server-side. Configure credentials above, then enter your gateway URL.

Saved automatically to browser storage.

bulkMutateAnOrganizationSIssues
PUT/api/0/organizations/{organization_id_or_slug}/issues/
Bulk mutate various attributes on a maxmimum of 1000 issues. - For non-status updates, the `id` query parameter is required. - For status updates, the `id` query parameter may be omitted to update issues that match the filtering. If any IDs are out of scope, the data won't be mutated but the endpoint will still produce a successful response. For example, if no issues were found matching the criteria, a HTTP 204 is returned.

Parameters

required

The ID or slug of the organization the resource belongs to.

The name of environments to filter by.

The IDs of projects to filter by. `-1` means all available projects. For example, the following are valid parameters: - `/?project=1234&project=56789` - `/?project=-1`

The list of issue IDs to mutate. It is optional for status updates, in which an implicit `update all` is assumed.

An optional search query for filtering issues. A default query will apply if no view/query is set. For all results use this parameter with an empty string.

The ID of the view to use. If no query is present, the view's query and filters will be applied.

The sort order of the view. Options include 'Last Seen' (`date`), 'First Seen' (`new`), 'Trends' (`trends`), 'Events' (`freq`), 'Users' (`user`), 'Date Added' (`inbox`), and 'Recommended' (`recommended`).

The maximum number of issues to affect. The maximum is 100.

Input

required

If true, marks the issue as reviewed by the requestor.

required

Limit mutations to only issues with the given status. * `resolved` * `unresolved` * `ignored` * `resolvedInNextRelease` * `muted`

required

Additional details about the resolution. Status detail updates that include release data are only allowed for issues within a single project.

required

The new substatus of the issue. * `archived_until_escalating` * `archived_until_condition_met` * `archived_forever` * `escalating` * `ongoing` * `regressed` * `new`

required

If true, marks the issue as seen by the requestor.

required

If true, bookmarks the issue for the requestor.

required

If true, publishes the issue.

required

If true, subscribes the requestor to the issue.

required

If true, merges the issues together.

required

If true, discards the issues instead of updating them.

required

The user or team that should be assigned to the issues. Values take the form of `<user_id>`, `user:<user_id>`, `<username>`, `<user_primary_email>`, or `team:<team_id>`.

required

The priority that should be set for the issues * `low` * `medium` * `high`

Enter a gateway URL above to enable sending.

Code snippet
Updates live as you fill in the form above.

TypeScript

import sentry from '@utdk/sentry';

await sentry.bulkMutateAnOrganizationSIssues({
  "query": "is:unresolved",
  "sort": "date",
  "limit": 100
})